Method and System for Real-Time Insertion of Services During a Call Session Over a Communication Network

ABSTRACT

A method and apparatus for real-time insertion of services into an IP telephony call session are disclosed. A client initiates a service request message to a second server. The service request message includes the client identity and a requested service available from a second server. The first server determines if the client is authorized to use the requested service. If the client is authorized to use the requested service, the second server delivers the requested service to the client.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 09/751,811 filed Dec. 29, 2000 and entitled “Method and System for Real-Time Insertion of Services During a Call Session Over a Communication Network”.

TECHNICAL FIELD OF THE INVENTION

This invention relates in general to Internet Protocol (IP) telephony, and more particularly to a method and system for real-time insertion of services during a call session over a communication network.

BACKGROUND OF THE INVENTION

IP telephony uses the Internet Protocol (IP) to transmit voice as packets over any data network that supports IP. Traditional circuit switched networks, such as the public switched telephone network (PSTN), establish a call by setting up an end-to-end circuit between two telephones. The switched connection is established for the duration of the telephone call, with a fixed bandwidth. In contrast, an IP telephony connection digitizes, compresses and converts the voice signal into IP packets and transmits the packets over the data network. Numerous different calls may share the same network and each participant in a call may have a different bandwidth that varies over the duration of the call depending on the amount of data being communicated over the network at any given time.

Conventional phone service provided over the PSTN requires a subscriber to pay for long distance service based on the number of minutes for the call. Furthermore, if the subscriber would like to add a special service, such as caller id, call forwarding or call waiting, the subscriber typically pays a monthly fee for the service. This fee is paid to the telephone company even if the subscriber does not use the service during the month. IP telephony service operates in a similar way because the subscriber is limited to services provided by an Internet Service Provider (ISP) for a fee during a specific period.

SUMMARY OF THE INVENTION

In accordance with the teachings of the present invention, disadvantages and problems associated with real-time insertion of services during a call session over a communication network have been substantially reduced or eliminated. In a particular embodiment, Session-based Services Telephony Protocol (SSTP) for use in Internet Protocol (IP) telephony is disclosed that allows a user to add services, such as the ability to send data for use in a word processing application or the ability to increase the level of encryption provided, during an IP telephony call session by requesting a desired service from a server coupled to a packet-based network.

In accordance with one embodiment of the present invention, a method for real-time insertion of services during a call session over a communication network includes initiating a Service Request Message (SRM) by a first client to a first server. The SRM includes the first client identity and a requested service available from a second server including a plurality of services. Upon receiving the message, the first server determines if the first client is authorized to receive the requested service. If the first client is authorized to receive the requested service, the second server delivers the requested service to the first client.

In accordance with another embodiment of the present invention, a communication system for real-time insertion of services during a call session over a communication network includes a client, a first device and a second device coupled to a communication network. The first device includes a list of clients authorized to receive a plurality of services. The second device inserts one or more of the services requested by the client into the call session if the list includes the client and the requested service.

Important technical advantages of certain embodiments of the present invention include the ability to add services for use during a call session. In a conventional communication system, a subscriber may use an extra service installed on a network if the subscriber requests and pays for the service before beginning the call session. The present invention allows the subscriber to add one or more services during a call session. If the equipment used by the subscriber is not capable of receiving the requested service, the necessary software may be configured at a remote location, such as a server, and uploaded onto a cache, or other suitable memory, associated with the subscriber's equipment. When the call session is terminated or the subscriber disconnects from or breaks communication with the call session, the service and associated software may be deleted from the subscriber's equipment by flushing the cache.

Another important technical advantage of certain embodiments of the present invention includes the ability of a service provider to charge a subscriber for a requested service based on use of the requested service. When the subscriber requests to use a service, either by subscribing to the service for specific time period, requesting the service prior to initiating a call session, or requesting the service during the call session, the service provider creates an account for the subscriber. The account may contain usage tokens for the requested service. Each time the subscriber uses the requested service, a usage token is deleted from the subscriber's account. The service provider, therefore, may track usage of the service and bill the subscriber based on the number of tokens used.

Other technical advantages will be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a communication network incorporating one embodiment of the present invention;

FIG. 2A illustrates a block diagram of one embodiment for inserting a requested service into a call session;

FIG. 2B illustrates a block diagram of an alternative embodiment for inserting the requested service into the call session;

FIG. 2C illustrates a block diagram of a further embodiment for inserting the requested service into the call session;

FIG. 3 illustrates a flowchart of a method for real-time insertion of services into a call session over the communication network;

FIG. 4 illustrates a flowchart of a method for charging a client for use of the requested service.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a block diagram of a communication system 10 that supports real-time insertion of services during a call session over network 12. System 10 includes network 12, clients 14 and 16, and servers 18 and 20. Server 18 includes a list of services that may be requested by clients 14 and 16 during a call session and associated software applications to execute the services. Server 20 includes a database containing a list of clients that may couple to network 12 and the services available from server 18 that each client is authorized to receive. Clients 14 and 16 may request authorization from server 20 to use one or more services stored on server 18. If server 20 determines that clients 14 and 16 are authorized to use a requested service, server 18 sends the requested service to clients 14 and 16. Although servers 18 and 20 are described as being separate, the list of authorized clients and the services and their associated applications may be physically located on a single device, such as a server, router, call manager, or other suitable network control device.

Network 12 may be a local area network (LAN), a wide area network (WAN), the Internet or other similar network that transmits packets of voice, video, data and other information (generally referred to as media). In a particular embodiment, network 12 may be an Internet Protocol (IP) network. However, network 12 may be any type of network that allows transmission of audio and video telecommunication signals, as well as traditional data communications. Although the invention will be described primarily with respect to IP communications, it should be understood that other appropriate methods of transmitting media over a data network, such as a Frame Relay, Asynchronous Transfer Mode (ATM), or other packet-based network, are also included within the scope of the present invention.

Network 12 may be coupled to other IP networks and may communicate media between clients 14 and 16, and other clients (not expressly shown) located on different, but interconnected, IP networks (not expressly shown). Network 12 may also be coupled to non-IP communication networks through the use of gateway devices. For example, network 12 may be coupled to a private branch exchange (PBX) or the public switched telephone network (PSTN) through an appropriate gateway (not expressly shown). The gateway may digitize the telephone or data signal from the PBX or PSTN if it is not already digitized, compress the digitized signal and route it to a destination over network 12 in packet form. The gateway may also convert packets of data into telephone signals that may be transmitted across the PBX or PSTN.

IP networks and other packet-based networks typically transmit media by placing data in cells, packets, frames, or other portions of information (generally referred to as packets) and sending each packet individually to the selected destination. Unlike a circuit-switched network, such as the PSTN, dedicated circuits and bandwidth is not required for the duration of a call session over network 12. Instead, clients 14 and 16 may send packets across network 12 as these resources become available for transmission. This feature makes resources available for additional communications when media is not being transmitted from clients 14 and 16.

The technology that allows voice media in particular to be transmitted over a packet-based network may be referred to as Voice over Packet (VoP). Clients 14 and 16 have the capability to encapsulate a user's voice or other content into IP packets so that the content may be transmitted over network 12. Clients 14 and 16 may be IP telephones, computers running telephony software, gateway devices, or any other device capable of performing telephony functions in an IP network. Clients 14 and 16 may also include a cache or any other type of storage medium for storing software applications and digital information.

System 10 includes servers 18 and 20 that communicate with clients 14 and 16 via network 12. Servers 18 and 20 may have access to storage mediums that include databases of information. Multiple services and the applications required to support the services may be available from server 18. Server 18 may inject one or more of the services requested by clients 14 and 16 into a call session over network 12. Such services may include, but are not limited to, text documents, telephone numbers, URLs, encoded music, graphics and videos communicated between clients 14 and 16, encryption or increased encryption for packets communicated over network 12, division of a conference call into multiple subgroups, and any other service suitable to be transmitted across network 12 in packet form and used by clients 14 and 16 during a call session. The applications available from server 18 may include, but are not limited to, light weight versions of a text editor, a spreadsheet tool, and a presentation tool similar to what can be found in MICROSOFT OFFICE application suite, ACROBAT READER, web browsers (e.g., NETSCAPE or MICROSOFT EXPLORER), a software application that plays music, a software application that allows a user to view a graphic or a photograph on a monitor, a software application that allows a user to view a movie, a software application that provides increased encryption for packets communicated over network 12, a software application that allows a user to break down a conference call into subgroups, or any other suitable application that may be configured at a remote location, such as server 18, transmitted in packet form over network 12 and executed by clients 14 and 16 during the call session.

Server 20 includes a list or directory containing clients that may communicate with network 12 and the services available from server 18 that each client is authorized to use. When clients 14 and 16 are connected to network 12, clients 14 and 16 may be assigned an IP address using dynamic host control protocol (DHCP) (not expressly shown) or another similar protocol or technique.

In one embodiment, clients 14 and 16 issue a registration request to server 20 by submitting their respective IP addresses and their identities in the form of a digital certificate, a username and/or password, or any other suitable way of providing identification information. Server 20 authenticates clients 14 and 16 by submitting the IP addresses to a DHCP server and the client identity information to an authentication system such as a Public Key Infrastructure (PKI) certificate authority, a Kerberos Domain Controller (KDC), or any other system suitable for authenticating the identity of a client or a user. If clients 14 and 16 are authenticated, the authentication system sends the authenticated credentials for clients 14 and 16 to server 20 and server 20 stores the credentials in the list.

Once the authenticated credentials for clients 14 and 16 are stored on server 20, the services available from server 18 may be added to the list. In one embodiment, client 14 may subscribe to the desired service from a service provider and may have pre-existing authorization to use one or more of the services available from server 18 for each call session initiated during a specific time period. In this example, the services may be added to the list on server 20 by the service provider and remain in the list until client 14 terminates the subscription for the service.

In another embodiment, client 14 may subscribe to a service provider for communication over network 12 but may not subscribe to any services available from server 18. After initiating a call session, client 14 may decide to add one of the services stored on server 18 to the call session. Server 20 authenticates client 14 and adds the requested service to the list of services that client 14 is authorized to use. The requested service may be removed from the list when server 20 receives a message indicating that the call session was terminated or client 14 disconnected from or otherwise broke communications with the call session.

In a further embodiment, client 14 may contact a service provider prior to initiating a call session to request a service available from server 18. In this example, the service provider may add the requested service into the list of clients stored on server 20 so that client 14 will be authorized to receive the requested service when the call session is initiated. If client 14 requests authorization to use the service for more than one call session, the service provider adds the requested service to the list stored on server 20 and specifies the number of times that client 14 may use the service. For example, if client 14 requests to use the service four different times, the service provider updates the authorization list on server 20 to reflect that client 14 is authorized to use the requested service four times. When server 20 receives a SRM from client 14 to use the requested service, server 20 authorizes client 14 to use the requested service during the call session and deletes an entry from the list authorizing client 14 to use the requested service. The updated list contains authorization for client 14 to use the requested service three additional times.

Although subsequent description refers to clients 14 and 16 as the participants in a call session, other clients coupled to network 12 or other networks coupled to network 12 may participant in the call session. During a call session, client 14 obtains a list of services available from server 18 and determines the IP address for client 16, which is participating in the call session. In one embodiment, client 14 may receive the list of services available from server 18 after being authenticated and authorized to use the services by server 20. Client 14 then initiates a Service Request Message (SRM) to server 20 to obtain authorization to use one or more requested services during the call session. In one embodiment, the SRM may include the requested service and the client identity for client 14 in the form of a digital certificate, username and/or password, or any other suitable means for providing identification information.

Server 20 authenticates client 14 by comparing the client identity with a list containing the authenticated credentials for each client that may communicate with network 12. If authentication fails, server 20 rejects the SRM from client 14. If the client identity matches one of the authenticated credentials in the list, server 20 determines if client 14 is authorized to use the requested service. If client 14 is not authorized to use the requested service, server 20 rejects the SRM from client 14. If client 14 is authorized to use the requested service, server 20 sends an authorization ticket to client 14. In one embodiment, the authorization ticket includes the client identity for client 14 and the requested service.

Client 14 sends the authorization ticket to server 18. In one embodiment, client 14 also sends the IP address associated with client 16 to server 18. Server 18 reads the authorization ticket and retrieves the requested service. Server 18 then sends the requested service to client 14 based on the client identity in the authorization ticket and to client 16 by using the IP address received from client 14. Although client 14 has been described as the requesting client, it should be understood that client 16, or any other client participating in the call session, may perform the described functions.

In one embodiment, clients 14 and 16 may not include the software application required to execute the requested service. Server 18 may configure the application associated with the requested service for use by clients 14 and 16 and load the required application into a cache or other suitable memory associated with clients 14 and 16. In another embodiment, client 14 may have access to the software application associated with the requested service, but client 16 may not have access to the application. If client 14 is authorized to use the requested service, server 18 may configure the software application associated with the requested service for client 16 and load the required application into the cache or other suitable memory associated with client 16.

In one embodiment, the software application and its associated service are transmitted over network 12 in packet form. Each packet travels through a protocol stack at the source and destination devices. The protocol stacks may be based on the Open System Interconnection Reference model (OSI model). The OSI model defines the communication characteristics for any given computer network and breaks communication between clients 14 and 16 coupled to network 12 into seven specific layers. The upper layers of the protocol stack are typically implemented in software and include the session layer, the presentation layer and the application layer. The session layer ensures that communication sessions, including service requests and service responses between applications, are properly established and maintained. The presentation layer manipulates the packets of information and ensures that information sent from the application layer for client 14 will be readable by the application layer of client 16. The application layer acts as a user interface for clients 14 and 16 to access network 12 services.

The services and applications available from server 18 may be inserted into the call session in one of the upper layers of the protocol stack. If the requested service is inserted into the call session, more media information is being transmitted between clients 14 and 16. Due to the increased media, client 14 may make a request for more bandwidth. In one embodiment, the request for more bandwidth may be made using the Resource Reservation Protocol (RSVP). RSVP is a network-control protocol that enables networks to obtain special qualities of service (QoS) for the media flow across the network. RSVP operates in conjunction with routing protocols in the transport layer of the protocol stack. If an RSVP server determines that the bandwidth for the call session may be increased, an acknowledgement message may be sent to client 14 indicating that the bandwidth has been increased. Otherwise, the RSVP server notifies client 14 that a best-effort mode may be used for communication on network 12. If the minimum required bandwidth is available, the call session provisioning proceeds by using the bandwidth to transfer the service over network 12 and between clients 14 and 16.

Referring to FIGS. 2A through 2C, communication between servers 18 and 20 and clients 14 and 16 may occur over a single communication medium or multiple different communication mediums. The communication medium may be twisted pair wire, coaxial cable, fiber optic links, or any suitable communication medium for transmitting packets of information over network 12.

FIG. 2A illustrates a block diagram of one embodiment for real-time insertion of services into a call session. In the illustrated embodiment, client 14 initiates SRM 30 to server 20. SRM 30 includes the client identity associated with client 14 and one or more requested services available from server 18. Server 20 determines if client 14 is authorized to use the requested services by comparing the client identity and the requested services with a list and/or directory. The list includes authenticated credentials for each client that may communicate with network 12 and the services available from server 18 that each client is authorized to use. If server 20 determines that client 14 is authorized to use the requested services, server 20 sends authorization ticket 32 to client 14. Authorization ticket 32 includes the client identity and the requested services. In one embodiment, server 20 encrypts authorization ticket 32 using its private key.

Upon receiving authorization ticket 32, client 14 determines the IP address for client 16. Client 14 then sends authorization message 34 to server 18. Authorization message 34 includes the client identity and the requested services from authorization ticket 32, and the IP address for client 16. Server 18 decrypts authorization message 34 with a public key associated with server 20 and reads authorization message 34 to retrieve the requested services. Server 18 then sends service message 36 in a secure manner to client 14 by using the client identity from authorization message 32 and service message 38 to client 16 based on the IP address. Service messages 36 and 38 include the requested services from authorization message 34.

FIG. 2B illustrates a block diagram of an alternative embodiment for real-time insertion of services into a call session. In the illustrated embodiment, client 14 determines the IP address for client 16. In one embodiment, the IP address for client 16 may be obtained from a call manager (not expressly shown) coupled to network 12. Client 14 initiates SRM 40 to server 20 that includes the client identity associated with client 14, one or more requested services, and the IP address for client 16. Server 20 determines if client 14 is authorized to use the requested services by comparing the client identity and the requested services with a list of authorized clients.

If client 14 is authorized to use the requested services, server 20 sends authorization ticket 42 to server 18. By sending authorization ticket 42 to server 18, server 20 reduces the amount of communication occurring over network 12. Authorization ticket 42 includes the client identity associated with client 14, the requested services, and the IP address for client 16. In one embodiment, server 20 encrypts authorization ticket 42 using its private key. Server 18 decrypts authorization ticket 42 using a public key associated with server 20 and retrieves the requested services based on authorization ticket 42. Server 18 then sends service message 44 to client 14 based on the client identity in authorization ticket 42 and service message 46 to client 16 by using the IP address for client 16. Service messages 44 and 46 include the requested services from authorization ticket 42.

In an alternative embodiment, once server 20 determines that client 14 is authorized to use the requested service, server 20 uses the IP address to request a client identity for client 16. Client 16 receives the request and sends its identity to server 20. Server 20 compares the client identity for client 16 and the requested service with the list of authorized clients. If client 16 is authorized to use the requested service, server 20 sends authorization ticket 42 to server 18. The authorization ticket includes the client identities for clients 14 and 16, and the requested services. Server 18 reads authorization ticket 42 and sends the requested services to clients 14 and 16 based on the respective client identities.

FIG. 2C illustrates a block diagram of a further embodiment for real-time insertion of services into a call session. In the illustrated embodiment, client 14 determines the IP address for client 16. Client 14 initiates SRM 50 to server 20 that includes the client identity associated with client 14, one or more requested services, and the IP address for client 16. Server 20 determines if client 14 is authorized to use the requested services by comparing the client identity and the requested services with a list of authorized clients.

If client 14 is authorized to use the requested services, server 20 locates client 16 based on the IP address in the service request message and sends identity request message 52 to client 16. Client 16 sends client message 54, containing its identification information, to server 20. Server 20 compares the client identity for client 16 to the list of authorized clients. If client 16 is authorized to use the services requested by client 14, server 20 issues first authorization ticket 56 to client 14 and second authorization ticket 58 to client 16. First authorization ticket 56 includes the client identity associated with client 14 and the requested services, and second authorization ticket 58 includes the client identity associated with client 16 and the requested services. In one embodiment, first authorization ticket 56 and second authorization ticket 58 includes an application resource locator (ARL) that informs clients 14 and 16 where the requested services may be located. In one embodiment, server 20 encrypts first authorization ticket 56 and second authorization ticket 58 using its private key.

In an alternative embodiment, call session may include other participants and server 20 may obtain client identities for these participants. If client 14 is the only participant in the call session authorized to use the request services, server 20 denies SRM 50. If all clients are authorized to use the requested services, server 20 sends an authorization ticket to each client participating in the call session. If at least one of the clients is not authorized to use the requested services, server 20 sends a message to client 14 asking if client 14 wishes to proceed using the requested services with those clients that are authorized. If client 14 decides to use the requested services, server 20 sends an authorization ticket to the authorized clients, while the at least one unauthorized continues to participate in the call session without the added services.

In one embodiment, network 12 may be a WAN and clients 14 and 16 may be coupled to network 12 in different physical locations. In this example, server 18 a may communicate with client 14 and server 18 b may communicate with client 16. In one embodiment, client 14 may decrypt first authorization ticket 56 with a public key associated with server 20 and client 16 may decrypt second authorization ticket 58 using the public key for server 20. Client 14 re-encrypts first authorization ticket 56 with its private key and sends first authorization message 60 to server 18 a. Using a similar method, client 16 re-encrypts second authorization ticket 58 with its private key and sends second authorization message 62 to server 18 b via. Server 18 a decrypts first authorization message 60 with a public key associated with client 14 and server 18 b decrypts second authorization message 62 with a public key associated with client 16. Server 18 a reads first authorization message 60 and server 18 b reads second authorization message 62 to retrieve the requested services. Server 18 a sends first service message 64 to client 14 and server 18 b sends second service message 66 to client 16. Service messages 64 and 66 include the requested services from authorization messages 60 and 62, respectively.

In an alternative embodiment, once server 20 determines that client 14 is authorized to use the requesting service, server 20 sends first authorization ticket 56 to client 14 and second authorization ticket 58 to client 16. First authorization ticket 56 includes the client identity for client 14 and the requested services, and second authorization ticket 58 includes the requested services. Client 14 sends first authorization message 60 to server 18 a, and client 16 sends second authorization message 62 to server 18 b. First authorization message 60 includes the client identity for client 14 and the requested services, and second authorization ticket includes the requested services and the IP address associated with client 16. Server 18 retrieves the requested services based on first authorization message 60 and server 18 b retrieves the requested services based on second authorization message 62. Server 18 a delivers the requested service to client 14 via first service message 64 by using the client identity for client 14 and server 18 b delivers the requested services to client 16 via service message 66 based on the IP address associated with client 16.

FIG. 3 illustrates a flowchart of a method for real-time insertion of services during a call session over network 12. As shown, at step 80, client 14 obtains the IP address for client 16 and initiates a service request message to server 20 to obtain authorization to use a service available from server 18 during a call session at step 82. In one embodiment, the service request message includes the client identity for client 14 and the requested service. In an alternative embodiment, the service request message may also include the IP address associated with client 16. Server 20 receives the authorization request at step 84 and compares the client identity for client 14 and requested service with a list of clients and authorized services stored in a database associated with server 20.

Server 20 determines if client 14 is authorized to receive the requested service at step 86 based on the results of the comparison from step 84. If client 14 is not in the list, server 20 rejects the service request message at step 88 and sends a message denying client 14 authorization to use the requested service. If server 20 locates client 14 in the list but determines that client 14 is not authorized to use the requested service, server 20 denies the request and sends a message to client 14 rejecting the request at step 88. If server 20 locates client 14 in the list and determines that client 14 is authorized to use the requested service, server 20 sends an authorization ticket to client 14 at step 90. In one embodiment, the authorization ticket includes the client identity associated with client 14 and the requested service.

At step 92, client 14 sends the authorization ticket to server 18 to obtain the requested service. In one embodiment, client 14 may also send the IP address for client 16 to server 18 with the authorization ticket. Upon receiving the authorization ticket, server 18 reads the authorization ticket to retrieve the requested service in the database at step 94. Server 18 delivers the requested service to client 14 based on the client identity in the authorization ticket and to client 16 using the IP address associated with client 16. In one embodiment, the application to execute the requested service may not be installed on a cache or other suitable memory associated with each of clients 14 and 16. Server 18 may configure the requested service and upload the application to the caches associated with clients 14 and 16.

At step 98, server 20 determines if the call session has ended or clients 14 and 16 have disconnected from the call session. If the call session has ended, the requested service is removed from clients 14 and 16 by flushing the cache or other suitable memory associated with each of clients 14 and 16.

FIG. 4 illustrates a flowchart of a method for charging clients 14 and 16 to use a requested service. At step 110, server 20 determines that clients 14 and 16 are authorized to use the requested service. When server 18 sends the requested service to clients 14 and 16, server 18 requests usage tokens from clients 14 and 16. In one embodiment, each usage token allows clients 14 and 16 to use the requested service during one call session. In an alternative embodiment, the usage token may allow clients 14 and 16 to use the requested service for a predetermined number of minutes. In another embodiment, tokens for clients 14 and 16 may be stored on server 20 and obtained by either clients 14 and 16 or server 18. If server 18 obtains a token from clients 14 and 16 at step 112, clients 14 and 16 delete one token from their respective accounts at step 114. If server 18 does not obtain a token from both clients 14 and 16 at step 112, server 18 requests a usage token from the requesting client, e.g., client 14, for both clients 14 and 16 at step 116. If client 14 provides server 18 with tokens for clients 14 and 16, client 14 deletes two tokens from its account. If client 14 does not provide server 18 with two tokens, client 14 deletes the remaining tokens in its account at step 120. Server 18 then charges the account associated with client 14 for the additional token at step 122.

Although the present invention has been described with several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present invention encompass such changes, variations, alterations, transformations, and modifications as fall within the scope of the appended claims. 

1. A method for real-time insertion of services during a call session over a communication network, comprising: initiating a service request message by a first client to a first server, the service request message including the first client identity and a requested service available from a second server comprising a plurality of services; determining if the first client is authorized to use the requested service at the first server; and delivering the requested service to the first client by the second server if the first server determines that the first client is authorized to use the requested service.
 2. The method of claim 1, wherein at least one of the services comprises an application operable to provide text viewing and modification capabilities.
 3. The method of claim 1, wherein at least one of the services comprises an application operable to provide graphic viewing and modification capabilities.
 4. The method of claim 1, wherein at least one of the services comprises an application operable to provide increased security during a call session.
 5. The method of claim 1, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; and issuing a ticket to the first client if the list includes authorization for the first client to use the requested service.
 6. The method of claim 1, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; issuing a ticket to the first client if the list includes authorization for the first client to use the requested service, the ticket including the first client identity and the requested service; sending the ticket to the second server by the first client; and reading the ticket at the second server to retrieve the requested service.
 7. The method of claim 1, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; issuing a ticket to the first client if the list includes authorization for the first client to use the requested service, the ticket including the first client identity and the requested service; sending the ticket and an address associated with a second client to the second server by the first client; reading the ticket at the second server to retrieve the requested service; and delivering the requested service to the second client based on the address received from the first client.
 8. The method of claim 1, wherein the service request message further comprises an address associated with a second client.
 9. The method of claim 8, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; and issuing a ticket to the second server if the list includes authorization for the first client to use the requested service.
 10. The method of claim 8, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; issuing a ticket to the second server if the list includes authorization for the first client to use the requested service, the ticket including the first client identity, the requested service, and the address associated with the second client; reading the ticket at the second server to retrieve the requested service; and delivering the requested service to the second client based on the address included in the ticket.
 11. The method of claim 8, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; obtaining the second client identity based on the address included in the service request message if the list includes authorization for the first client to use the requested service; comparing the second client identity and the requested service with the list stored in the first server; issuing a ticket to the second server if the list includes authorization for the second client to use the requested service, the ticket including the first client identity, the second client identity, and the requested service; reading the ticket at the second server to retrieve the requested service; and delivering the requested service to the second client based on the second client identity.
 12. The method of claim 1, further comprising pressing a button associated with the requested service at the first client during a call session to initiate the service request message.
 13. The method of claim 1, further comprising selecting the requested service from a menu displayed on the first client during a call session to initiate the service request message.
 14. A communication system, comprising: a client operable to couple to a communication network; a first device operable to couple to the communication network, the first device comprising a list of clients authorized to use at least one of a plurality of services; and a second device operable to couple to the communication network, the second device further operable to insert one or more of the services requested by the client into a call session if the list includes the client and a requested service.
 15. The communication system of claim 14, wherein the client further comprises a cache operable to store a requested service and the requested service removable from the cache when the call session terminates.
 16. The communication system of claim 14, wherein the first device is operable to determine if the client is authorized to use the requested service.
 17. The communication system of claim 14, wherein at least one of the services comprises an application operable to provide text viewing and modification capabilities.
 18. The communication system of claim 14, wherein at least one of the services comprises an application operable to provide graphic viewing and modification capabilities.
 19. The communication system of claim 14, wherein at least one of the services comprises an application operable to provide increased security during the call session.
 20. The communication system of claim 14, wherein the first device is operable to: receive a service request message from the client, the service request message including the client identity and the requested service; compare the client identity and the requested service with the list; and issue a ticket to the client if the list includes authorization for the client to use the requested service.
 21. The communication system of claim 14, wherein the first device is operable to: receive a service request message from the client, the service request message including the client identity, the requested service, and at least one address associated with at least one additional client; compare the client identity and the requested service with the list; and issue a ticket to the second device if the list includes authorization for the client to use the requested service.
 22. The communication system of claim 14, further comprising: a plurality of remote clients coupled to the communication network; and a plurality of remote second devices coupled to the communication network, each remote second device associated with at least one of the remote clients.
 23. The communication system of claim 22, wherein the first device is operable to: receive a service request message from the client, the service request message including the client identity, the requested service, and at least one address associated with at least one remote client; compare the client and the requested service with the list; and issue a ticket to the client and each of the remote clients if the list includes authorization for the client to use the requested service.
 24. The communication system of claim 22, wherein: the first device is operable to: receive a service request message from the client, the service request message including the client identity, the requested service, and at least one address associated with at least one remote client; compare the client and the requested service with the list; and issue a ticket to the client and each of the remote clients if the list includes authorization for the client to use the requested service, each of the tickets including the respective client identity and the requested service; the client is operable to send the ticket to the second device; and the remote clients are operable to send the tickets to the remote second device associated with each of the remote clients.
 25. The communication system of claim 22, wherein the first device is operable to: receive a service request message from the client, the service request message including the client identity, the requested service, and at least one address associated with at least one remote client; compare the client identity and the requested service with the list; obtain at least one remote client identity based on the address included in the service request message if the list includes authorization for the client to use the requested service; compare the remote client identity and the requested service with the list; and issue a ticket to each of the authorized clients if the list includes authorization for at least one of the remote clients to use the requested service.
 26. The communication system of claim 22, wherein: the first device is operable to: receive a service request message from the client, the service request message including the client identity, the requested service, and at least one address associated with at least one remote client; compare the client identity and the requested service with the list; obtain at least one remote client identity based on the address from the service request message if the list includes authorization for the client to use the requested service; compare the remote client identity and requested service with the list; and issue a respective ticket to the client and each of the authorized remote clients if the list includes authorization for at least one of the remote clients to use the requested service, each of the tickets including the respective client identity and the requested service; the client is operable to send the ticket to the second device; and the remote clients are operable to send the tickets to the remote second device associated with each of the remote clients.
 27. The communication system of claim 14, wherein the client comprises a button operable to initiate a service request message during the call session.
 28. The communication system of claim 14, wherein the client comprises a menu operable to select the requested service during the call session.
 29. Logic encoded in media for real-time insertion of services during a call session over a communication network and operable to perform the following steps: initiating a service request message by a first client to a first server, the service request message including the first client identity and a requested service available from a second server comprising a plurality of services; determining if the first client is authorized to use the requested service at the first server; and delivering the requested service to the first client by the second server if the first server determines that the first client is authorized to use the requested service.
 30. The logic encoded in media of claim 29, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; and issuing a ticket to the first client if the list includes authorization for the first client to use the requested service.
 31. The logic encoded in media of claim 29, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; issuing a ticket to the first client if the list includes authorization for the first client to use the requested service, the ticket including the first client identity and the requested service; sending the ticket to the second server by the first client; and reading the ticket at the second server to retrieve the requested service.
 32. The logic encoded in media of claim 29, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; issuing a ticket to the first client if the list includes authorization for the first client to use the requested service, the ticket including the first client identity and the requested service; sending the ticket and an address associated with a second client to the second server by the first client; reading the ticket at the second server to retrieve the requested service; and delivering the requested service to the second client based on the address received from the first client.
 33. The logic encoded in media of claim 29, wherein the service request message further comprises an address associated with a second client.
 34. The logic encoded in media of claim 33, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; and issuing a ticket to the second server if the list includes authorization for the first client to use the requested service.
 35. The logic encoded in media of claim 33, further comprising: comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; issuing a ticket to the second server if the list includes authorization for the first client to use the requested service, the ticket including the first client identity, the requested service and the address associated with the second client; reading the ticket at the second server to retrieve the requested service; and delivering the requested service to the second client based on the address included in the ticket.
 36. An apparatus for real-time insertion of services during a call session over a communication network, comprising: means for initiating a service request message by a first client to a first server, the service request message including the first client identity and a requested service available from a second server comprising a plurality of services; means for determining if the first client is authorized to use the requested service at the first server; and means for delivering the requested service to the first client by the second server if the first server determines that the first client is authorized to use the requested service.
 37. The apparatus of claim 36, further comprising: means for comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; means for issuing a ticket to the first client if the list includes authorization for the first client to use the requested service, the ticket including the first client identity and the requested service; means for sending the ticket to the second server by the first client; and means for reading the ticket at the second server to retrieve the requested service.
 38. The apparatus of claim 36, wherein the service request message further comprises an address associated with a second client.
 39. The apparatus of claim 38, further comprising: means for comparing the first client identity and the requested service with a list stored in the first server, the list comprising a plurality of clients authorized to use at least one of the services available from the second server; means for issuing a ticket to the second server if the list includes authorization for the first client to use the requested service, the ticket including the first client identity, the requested service, and the address associated with the second client; means for reading the ticket at the second server to retrieve the requested service; and means for delivering the requested service to the second client based on the address included in the ticket. 